Do controllers draw more power than keyboards? I wonder if, in spite of upgrading the power, there is actually a power issue. I'm not sure why the power symbol isn't showing if that is the case though.

Could be, usually a keyboard/mouse need about 100 mA, while a gamepad may require more.

There was a topic a while ago (see here) that surveyed the power usage for various controllers. It has the command to query the power the controller reported as needed, you can run the command and see what's reported by the Xbox controller.

At one time, there was a max_usb_current option for the PI (in config.txt) which increased the power offered by the USB port (600 -> 1200 mA), but now it's on by default and so it's not needed anymore.

Is it possible something I copied over from the previous Pi isn't playing nice? I thought I only copied over saves/emulator specific settings, but in the absence of anything else I wonder if something is getting in the way.

Highly unlikely - flashing a new image showed it's not that.

Thanks, now it works. :D

@zappyowl2482 those instructions are correct and current for official retropie. we do not install third party builds like those on twister os.

@mitu said in My Xbox controller stay off when my raspberry pi 4 get turned on:

The Pi4 and Pi3 are different hardware and have different USB controllers, hence the difference. That's not why your controller behaves this way.

There must be some difference somehow. I tried 2 different controllers: Xbox One Series X controller and Xbox One S controller ("S" not "Series S"). I tried all 4 usb ports. Everything work fine on my Pi 3 but none of them get turned on when my Pi 4 boot.

I think I will move on, anyway I planned to use the Xbox One wireless dongle and buy batteries + a docking station for refilling the batteries, so this problem shouldn't bother me anymore after that. I'm just leaving as much information as possible in case someone else encounter the same problem in the future.

Thanks for your help.

@lostless You’re right - it works instantly now. I was looking for a solution before posting, but somehow this post didn’t come up. It probably should be pinned somewhere.

Thanks!

Yes, I think I've seen a couple posts about using the driver successfully with RetroPie.

@quicksilver Will give it a try and report back. Thank you!

The wireless Xbox dongle are not supported by default, since there's no driver. There is a recent project that aims to add support for it - you should check out https://github.com/medusalix/xow.

Well I found a sollution from 2016 that worked for me, in this example it´s the snes that made trouble but it works for other emulators too

BuZz ADMINISTRATORS 24 Aug 2016, 17:19
@Robust

Please try the following.

From a terminal please do rm /opt/retropie/configs/snes/retroarch.cfg or delete the file over windows networking
Go to Emulation Station -> RetroPie and do Update RetroPie-Setup script
Go to Manage Packages -> Main section > lr-snes9x-next - and choose "Update from binary"
and all should be good.

@mitu said in RetroPie controller set up issue:

@ranma The problem in this topic is specific to the xpad driver, which powers the Xbox 360/One controllers, it's not a general one.
Basically, after an update of kernel, the xpad RetroPie driver was not installed and overwritten by the default one, which is sometimes incomplete depending on the model. This has been reported after the 4.4 was released, but was fixed some time ago https://github.com/RetroPie/RetroPie-Setup/commit/f6e5a6d70512fc796a4fb535ddf1b44ea985db47.

Oh I see. I assumed as the Logitech F710 switch had to be set to X input rather than D that this issue was effectively the same as mine. I'll start a new thread when I decide to have another attempt and if the problem resurfaces. Many thanks. :-)

I will try that ASAP

bumpd

@Maynard

i reinstalled RetroPie 4.2, before i used v3.6 with xBoxdrv

I would recommend disabling Xboxdrv and only using the Xpad driver. There's an issue with the Xboxdrv and the Linux kernel(s) used since version 3.8.x of RetroPie.